Skip to content

docs(WO17): py leg landed — the py parser is generated from the same pinned .parg; WO17 complete - #435

Merged
ronaldtse merged 1 commit into
mainfrom
wo17-py-leg
Nov 11, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
wo17-py-leg

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Summary

WO17's final piece landed: interscript-ruby #843 merged — the py parser is generated from the same sha256-pinned .parg the ts parser uses (module-for-module port: grammar_source / parg_reader / peg with match-span recording for the byte-exact override key and failure diagnostics / actions). parse_isc's public API unchanged; the ~900-line hand scanner replaced.

Evidence: py-vs-py parity driver 434/434 identical-to-hand (canonical schema and raw field-for-field); the maps harness scores it exactly like the incumbent (411/434, same 23 files, zero status flips); the py failure set is byte-identical to a pristine origin/main run (18 pre-existing environment gaps); the golden additivity test replays green in-suite.

Owner-flagged: interpreter perf (434-file corpus ~86 s vs hand's ~7 s — closure-compilation follow-ups documented, semantics untouched), a fourth dormant grammar extension (use-in-pass splicing, py-suite-pinned), and the standing cross-runtime alignment decisions (when position, dep-name lenience, U-escapes).

WO17 is complete: all four steps landed. The .parg grammar is the single semantic source for the ts and py parsers, judged continuously by the parity harness and the maps-CI four-runtime additivity gates.

@ronaldtse
ronaldtse merged commit d458e6f into main Nov 11, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant